Fields: iParts gallery

These fields control the properties of the standard iMIS iParts that are defined in the system. By default, these fields are found in the following locations:

■ In a content record, click add content, click a gallery folder, and select one of the listed iParts to the content record. For an existing iPart, click the down triangle at the far right of the iPart's title bar, then choose Configure.

■ When using the Surf-to-Edit (STE), click the STE icon that relates to various iParts in the content records used in the content areas of the page. You must be logged on to the website and have Content Editor permissions in at least one content authority group (CAG).

When you configure an iPart directly from STE, the available Save options are:

■ Save: A Working version of the content record is saved. Publish the content record to make it the active version.

■ Save and Publish: This option is available if you have the Content Approver CAG permission. When you Save and Publish, your changes are immediately visible on any CM website that uses the content record.

■ Save and Submit for Approval: This option is available if you do not have the Content Approver CAG permission. When you Save and Submit for Approval, your changes are saved and a content publishing request is submitted to the content folder’s Content Approver.

When you configure an iPart from a content record, you only have the option to Save or Cancel. You can publish your changes from the content record or the Document System toolbar.

To work with iParts that have been added to a content record, click the drop-down arrow at the right of an iPart's title bar and choose from the following commands:

■ Configure - Displays a window that enables you to define the properties of the iPart. For example, performing this action for a Content Html iPart displays an HTML editor. In configuration, you can access Help (

) for most iParts. This detailed configuration documentation also appears in the iPart Reference.

■ Connect - Displays a connection editor that enables staff or consultants to define iPart connections. Connections allow one iPart to interact with another iPart on the same content record. Not all iParts support connections, so when configuring an iPart, open the Configuration Help to determine the iPart’s connection options.

When creating a new connection, the available connection types are listed, and a drop-down list enables you to select from the other iParts on the same content record. For example, to configure iPart A to act upon iPart B, create a connection, and set iPart A to be the Object Consumer. Set iPart B to be the Object Provider. Each iPart can only have one Consumer and one Provider per connection type. So an iPart can only act as an Object Provider for one other iPart, for example, not as an Object Provider for several other iParts.

The connection editor lists all current connection points for the iPart and allows you to define new connections. Each iPart (consumer and provider) displays the connection once it is defined. For example, if you select iPart A and connect it to iPart B, and then look at the connections for B, you will see the connection there as well. Connections can also be disconnected from here.

Currently, connections can be of four types: Object, Atom Object, Uniform Key, or String. The type of connection to use depends on the implementation by the iPart’s author. Please refer to the specific iPart’s Configuration Help for details.

■ Minimize - Collapses the iPart's preview box, instead displaying only the iPart's title bar.

Note: The content types defined in the system determine the behavior of ASP.NET iParts controls within iMIS. Each iParts control must have an associated content type, which tells iMIS how to create the corresponding iPart within the system, how to edit it, how to display it, how to publish it, and so on. The system-defined iParts in the Content gallery all have a corresponding content type. A special ContentWebUserControl content type is used as the default content type for all custom iParts that you add to a content record. You can optionally define entirely new content types to enable more sophisticated system handling of a custom iPart that has been added to a content record.

■ Modifications to your master pages may be required if iParts appear to overflow the boundaries of iPart zones in the rendered pages. In general, this requires modifying the template's master page and accompanying CSS files to make the Home page and interior page layouts larger than their default size.

■ Custom ASP.NET iParts are not described in this section because they are not part of the standard set of iParts shipped with iMIS.

■ Implementers can add an ad hoc ASP.NET web user control to a content record by entering the relative path to the iPart in the Or, enter a path to a web user control field.

Specifies a relative URL from the root (~) of the physical path for the IIS application or IIS web site that hosts your CM websites to a web user control that you want to insert into this content record. By default, the root corresponds to C:\Program Files\ASI\iMIS\Net. For example, ~/CustomControls/myUserControl.aspx.